Skip to content

Conversation

sivanov-nuodb
Copy link
Collaborator

@sivanov-nuodb sivanov-nuodb commented Jun 10, 2025

Changes

This change adds pages to the troubleshooting runbook, which are referenced by
NuoDB operator alerts.

See rendered docs here.

Inspect the database components state.

```sh
kubectl get database acme-messaging-demo -o jsonpath='{.status.components}' | jq
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

jq is only used for pretty-printing?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right. I couldn't find similar option for kubectl.

Copy link
Contributor

@kontaras kontaras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I had a couple grammar nitpicks.

Copy link
Collaborator

@adriansuarez adriansuarez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Just left some comments about typos and minor suggestions.

Copy link
Contributor

@kontaras kontaras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple more nit picks

Upon startup, SM processes perform a journal recovery procedure by applying any transaction messages to the atoms.
This involves extensive disk IO and may continue for a while depending on the backlog of messages and the number of atoms to which they are applied.
Upon startup, SM processes perform a journal recovery.
This may be time consuming if there are many journal entries to recover.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: It can also be time consuming is the storage is very slow.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, this is listed in the possible causes below.

@sivanov-nuodb sivanov-nuodb merged commit 066bf25 into main Jun 24, 2025
2 checks passed
@sivanov-nuodb sivanov-nuodb deleted the sivanov/DOC-4821 branch June 24, 2025 11:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants